Meeting Pearls 1/Meeting Pearls Vol 1 (1994).iso/installed_progs/text/faqs/unixware-faq/text0002.txt

Text File | 1994-06-13 | 15.2 KB | 424 lines

As of this posting, there are eight (8) updates, not all of which will
you typically need.  These updates are to be applied to version 1.0
only; all changes have been merged into version 1.1.  The updates are
(listed by their file names on the UnixWare ftp archive server):

  updte1.tar - First UnixWare update
  updte2.tar - Update 1.0.2
  updte3.tar - Update 1.0.3
  upbnu4.tar - Basic Networking Utilities (uucp, serial comm, ttymon) Update 4
  mipx.tar - Newer, faster Merge IPX; must have Advanced Merge installed
  mhs.tar - Fixes to MHS mail services; replaces earlier mhs.tar versions
  atmtp.tar - NFS automounter update 1.0.4
  nsupdt.tar - NetWare API Library update 1.0.4, fixes NetWare automounter

The first four of these are those of greatest interest to Usenet
readers.  Note that all of updte1/updte2/updte3 need not be installed;
Update 1.0.3 includes effectively replaces, and adds to, Update 1.0.3.
Thus UnixWare sysadmins can simply install Update 1.0.3 after the
first update is installed, and leave out Update 1.0.2 altogether.

All of these are available from the UnixWare ftp archive server:

  ftp.novell.com:~ftp/pub/unixware/Updates

They are also available on ftp.novell.de.  Andrew Josey
([e-mail]) adds:

``and also from our automated mail server which carries binaries/sources etc
  for UnixWare and also mirrors the ftp sites.

  To get a list of Updates from our mail server:

    mail [e-mail]

  with a msg containing:

    begin
    reply   <your-email-address-here!>
    index Updates
    end


  Use send with a filename to request a file. Note that the requests are
  case sensitive, for example to get the latest BNU fix:

    send MIRRORS/ftp.novell.com/pub/unixware/Updates/updbnu4.tar

Subject: S13) How do I know which updates I've already got installed?

Don't laugh; some of us have systems whose vendors installed UnixWare
(including the FAQ maintainer :-).  Updates will show up as installed
packages; from the UnixWare desktop, double click:

  System_Setup->Application_Setup

Be patient while the installed applications are cataloged.  When you get the
browser showing installed packages, you will be able to see the installed
updates.

If you are the impatient sort, Andrew Josey ([e-mail]) suggests:

  I cancel the cataloging, and then hit

    View
      Installed Appl'ns
        All

  Which is usually quicker... and ok when you know you've not reinstalled
  anything new recently.

Subject: S14)  How can I make the `man' pages accessible from the command line?

The following symbolic links will enable users to access the standard
UNIX man pages without further action on their part:

  ln -s /usr/flib/books/man /usr/share/man
  ln -s /usr/flib/bin/fman /usr/bin/man

Subject: S15) Are there disk compression utilties for UnixWare?

Programmed Logic sells such a drop-in replacement compressed file
system that, among other things, can be installed as the root
partition and can be NFS-exported.  Programmed Logic claims that it
can double a file system's capacity.  For information on the Desktop
File System (DTFS), contact:

  Programmed Logic Corp.
  200 Cottontail Lane
  Somerset, NJ 08873
  [phone] Voice
  [phone] FAX
  Email:
  [e-mail] (For product inquiries)
  [e-mail] (For order placement)
  [e-mail] (technical support for registered users)

Subject: S16) How do I install a package downloaded from one of the ftp servers?

Rick Richardson ([e-mail]) explains:

  You can untar the stuff anywhere convenient, say,
  under /tmp, and then:

    pkgadd -d /tmp

  The pkgname is optional.  Note that the -d flag assumes that if the
  argument begins with a '/', then its a package in filesystem format.
  Otherwise, its a magic cookie (e.g. diskette1) to pick a storage device.
  I.E., this won't work:

    cd /tmp; pkgadd -d .

Subject: S17) How can I speed up the loading of Windows programs from floppies?

If you find yourself loading a Windows program more than once, for
whatever reason, you might appreciate Rick Richardson's "Handy trick #1427":

  Use the file manager to copy each
  installation floppy to d:\diskN where N is the disk number.
  Then, you can try to install a program as many times as you
  want without waiting for floppies.  Just run D:\DISK1\SETUP
  from the file manager.  At least with Word, setup seems
  to understand that the files aren't coming from floppies
  and will just proceed to install everything it needs
  from d:\disk1, d:\disk2, etc. without further prompting.

  Discovered purely by accident - I had the disks in
  d:\w1, d:\w2, etc. and after setup finished with w1,
  it said it couldn't find d:\disk2\somefile.  Aha I say!

(FAQ maintainer's observation: I believe this is how some Windows software is
organized on CD-ROMs for installation - that might be why the Windows setup
program understands it.)

Subject: S18) Why has fingertip librarian suddenly stopped working?

An authorization code file for flib inexplicably carried an expiration
date of 12/31/93.  There is a trivial fix for this:

  $ mv /usr/flib/authorization /usr/flib/authorization.old

flib should now work again.

DEVELOPER

Subject: D1) What books on UnixWare programming might I read/purchase?

First, the UNIX Press volumes:

  Title                                  ISBN #
  - Programming Series -
  UNIX Software Development Tools        0-13-017690-7
  Programming in Standard C              0-13-017666-4
  Programming with UNIX System Calls     0-13-017674-5
  Character User Interface Programming   0-13-042581-8
  Graphical User Interface Programming   0-13-042698-9
  Network Programming Interfaces         0-13-017641-9
  Device Driver Programming              0-13-042623-7
  STREAMS Modules and Drivers            0-13-066879-6
  Portable Device Interface              0-13-066838-9

  - Reference Series -
  Command Reference (a-l)                0-13-042699-0
  Command Reference (m-z)                0-13-042607-5
  Operating System API Reference         0-13-017658-3
  Windowing System Reference             0-13-017716-4
  System Files and Devices Reference     0-13-017682-6
  Device Driver Reference                0-13-042631-8

No UNIX programmer should be caught without the Stevens' books:

  Advanced Programming in the UNIX Environment
  W. Richard Stevens
  Addison-Wesley, 1992
  ISBN 0-201-56317-7

  UNIX Network Programming
  W. Richard Stevens
  Prentice Hall, 1990
  ISBN 0-13-949876-1

Donald Lewine's POSIX programming guide is also indispensable as a
reference for "which standard defines what API?" kind of questions:

  POSIX Programmer's Guide
  Donald Lewine
  O'Reilly and Associates, Inc.
  ISBN 0-937175-73-0

Subject: D2) Are there alternatives for programmers to the UnixWare SDK?

Programmers on tight budgets might consider the Prime Time Freeware
SDK for Intel SVR4.2, Issue 1-1, a "complete, stand-along development
system" for UnixWare and similar Intel SVR4.2 Unix systems.  This is a
Rock Ridge CD-ROM containing all the major GNU development tools (gcc,
gdb, &c), X, InterViews, Tk and "much much more", plus a 100+ page
user's guide.  Univel provided Prime Time with the necessary #include
files and static C libraries to make this product a usable standalone
system.

  Prime Time SDK for Intel SVR4.2, Issue 1-1
  ISBN 1-88 1957-12-8
  Steve Zwaska, Editor
  Prime Time Freeware
  370 Altair Way, #150
  Sunnyvale, CA 94086
  [phone] Voice
  [phone] FAX
  [e-mail]

Subject: D3) I installed the Prime Time SDK, and now I can't log in?!

Some permissions were not set properly by the SDK install.  The fix is
to su to root and:

  chmod -R go+rx /usr/include
  chmod -R go+rx /usr/lib

There is a sticker on the CD-ROM envelope informing users of this
need, but it seems to have been accidentally left off of some early
shipments.  Steve Zwaska ([e-mail]) notes of these trials and
tribulations:

  We have fixed all of the script problems for version 2-1 (mid-January
  release) and have added a bunch of stuff (YEA XFree86-2.0 is on there in
  pkgadd format!)

  There is a FTP site for the corrected Install scripts and make_links at
  ftp.netcom.com  - pub/ptsdk/movers.uu

Subject: D4) Will UnixWare version 1.1 bundle Motif?

Yes.  Motif 1.2 runtime libraries and the Motif Window Manager are
included in UnixWare 1.1.

Subject: D5) How do I avoid problems programming with the UCB compatibility libraries?

There are two problems that are typically encountered when
compiling/linking code that uses Berklisms:

- Undefined symbols at link time
- Incompatibilities between the SysV header files and the UCB libraries

C code using Berklisms such as index/rindex will generate "undefined
symbol" messages for each of the BSD-specific functions.  To get
around this, you have one of two options:

a) Compile with the "UCB" compiler (/usr/ucb/cc).  This is actually a shell
   script wrapper around the standard C compiler (/usr/ccs/bin/cc) that
   sets up the necessary #include and library paths.  This is the path to
   take if you want a more "pure" BSD environment for your development.

b) If you want a SysV environment, but need to link in some functions
   only available in the BSD library (eg, you'll replace gethostname() with
   uname() later), simply link in the UCB libraries _after_ the standard
  (SysV) libraries.  For example:

     cc -o foo foo.c -lc -L /usr/ucblib -lucb

   Note the order of the library specifications, and that "-lc" should
   precede the UCB library specification to resolve all possible synonyms
   against the SysV library, rather than the BSD library.

Be careful exercising option (b), however.  Merely linking against the
UCB library, without the preceding "-lc", will cause code to be
compiled against the SysV #include files (located in /usr/include) and
then linked against the UCB libraries:

    cc -o foo foo.c -L /usr/ucblib -lucb  # Don't do this

(Note that an implicit "-lc" is appended to the command line.)
Differences in such things as structure sizes between the SysV
#includes and the UCB libraries can wreak all kinds of havoc - as your
friendly FAQ maintainer discovered in just this fashion when trying to
use setjmp in a source module that also called some UCB functions.
One way to get around this is to insert a "-I /usr/ucbinclude"
directive into the command line, but this is essentially the effect of
using /usr/ucb/cc.

On this general topic, I'll include some notes from the net.

Gordon W. Ross <[e-mail]> observes:

  I just wanted to mention here that most people I have helped with
  porting problems related to the dirent or directory libraries have
  caused their own problems by incorrectly using the UCB library.
  The directory(3) routines in the UCB library only work with the
  header files in /usr/ucbinclude so if you fail to put that in
  your include path and just link with -lucb you end up with
  seriously broken programs.  The stuff in /usr/ucbinclude/ and
  /usr/ucblib/ was meant to be used by /usr/ucb/cc only, and
  when used that way it (mostly) works.  I have usually found it
  easiest to just stay away from the UCB library entirely.
  I would advise others to do the same.  (The UCB library has
  well known problems in signal and some dbm functions.)

Robert Withrow ([e-mail]) adds:

  In addition, checking the following things will almost always yield a
  working port for any reasonably ``well behaved program'':

  1 Replace bcopy et.al with the apropriate memcpy functions...

  #define bcopy(b1,b2,len) memmove((b2), (b1), (size_t)(len))
  #define bzero(b,len) memset((b), 0, (size_t)(len))
  #define bcmp(b1,b2,len) memcmp((b1), (b2), (size_t)(len))

  2 Replace index and rindex approprately:

  #define index(a,b) strchr((a),(b))
  #define rindex(a,b) strrchr((a),(b))

  3 Don't use the SVR4 library's signal() routine,
  [use sigaction instead ...]

  /* Reliable signals */
  /* This was taken from Stevens... */

  #include <signal.h>

  typedef void Sigfunc(int);

  Sigfunc *signal(int signo, Sigfunc *func)
  {
    struct sigaction act, oact;

    act.sa_handler = func;
    sigemptyset(&act.sa_mask);
    act.sa_flags = 0;
    if (signo != SIGALRM) {
      act.sa_flags |= SA_RESTART;
    }
    if (sigaction(signo, &act, &oact) < 0)
      return(SIG_ERR);
    return(oact.sa_handler);
  }

  4 Replace random with lrand

  #define random() lrand48()
  #define srandom(seed) srand48((seed))

  5 Replace the bsd readdir code with the Posix code (requires changing an
  include file and a declaration usually, but also perhaps a symbol with a
  strlen.)

  6 Replace wait3 and wait4 with posix wait code.  This is complicated
  because some code *writes* into the values that posix only provides read
  access to.

Lest all this seem too dreadfully complicated, Rick Richardson
([e-mail]) shrugs:

  Its much easier to port stuff than most people think.

  I've found that 99.99% of applications with BSDisms can be ported
  by simply compiling normally, but linking with -lc -lucb.  This
  resolves the SVR4 C library first, avoiding problems with dirent
  and the like, but also lets you pick up any BSD-isms like
  random(), index(), etc.

  Really, its painless.

Subject: D6) Where can I get Emacs?

John Angelo Gnassi ([e-mail]) answers your prayers:

``If you live and die by Emacs, trying to get a new system up
  without it is torture.  You don't have to.  There is a version,
  18.59.5, in binary format ready for anonymous ftp from
  ftp.novell.com:/pub/unixware/developer/emacs.UWbin.tar.Z.  A pristine
  19.19 will not compile directly with the standard tools (preprocessor and
  other problems), but more than a half dozen people have told me they
  had no problems compiling it with gcc.''

The Prime Time SDK CD-ROM mentioned earlier also contains Emacs.

Subject: D7) How can I compile X clients without a complete X11 source tree?

Pat Campbell of Novell USG writes:

  To compile most if not all X clients WITHOUT a complete X tree
  use:
      imake -I/usr/X/lib/config -DUseInstalled
            ^^^^^^^^^^^^^^^^^^^
      Not necessary if you have set IMAKEINCLUDE environment variable.

  The "-DUseInstalled" directs imake to use the installed include
  and library files.

  Special note for motif applications:

  You will need three more libraries, -lXm -lXIM -lgen, during
  the link stage.  I prepend them to the following variables
  within the Imakefile like this.

               LOCAL_LIBRARIES = -lXm -lXIM [ whatever was already here ]
               SYS_LIBRARIES = -lgen [ whatever was already here ]

  This is a working solution, not necessarily the correct/elegant solution :-)

Subject: D8) I've now got 1.1.  Where's my SDK?

The UnixWare software development kit (SDK) ships separately from the
base UnixWare operating system.

Subject: D9) I've now got the 1.1 SDK.  Where's xab?

xab (X Application Builder) has been removed from the SDK distribution
as of release 1.1.  It is still available from ISC, however.

---
Trademarks

Unix is a registered trademark, licensed exclusively by X/Open Co., Ltd.
Novell, NetWare and UnixWare are trademarks of Novell, Inc.
Windows will probably become a trademark of Microsoft Corp. after all.
--
Jim Vlcek                         Elements of the information superhighway:
uunet!molly!vlcek                                        UNIX: the concrete
molly![e-mail]                             TCP/IP: the road signs
Beautiful downtown St. Paul                   Windows: the fast-food joints